The Crypto DevRel Trap (or how many users should you have when releasing an sdk)
The crypto DevRel trap (or how many users should you have when releasing an SDK) by malteish.eth5 🥝 • 2y • 0 views • 0 clicks | |
AI summary of the linked articleThe author, a DevRel professional, argues that crypto projects hire developer relations teams too early, before validating core use cases with users, and that this "DevRel Trap" slows mainstream adoption. The article cites a Telegram chat of over 400 crypto DevRels serving about 25,000 active blockchain developers, roughly one DevRel per 65 developers. It also compares Web2 companies, which launched consumer products 3 to 9 years before public APIs, such as Facebook (2004 consumer launch, 2007 API) and Airbnb (2008 launch, 2017 API). The proposed fix is to prioritize user-focused marketing and hire DevRels only once developers request API access. | |
Recommended by 2 curators | |
 Extremely heathly reformer content! If this gets implemented we‘re actually on a better trajectory as a space!  We def felt it with @timdaub.eth when we were at the ETHWarsaw hackathon. There were like 50 devs and 20 infra providers trying to convince devs to use their solution, even if it didn't make that much sense. I hope this essay will reach the right people :)  Sent it to the rest of our team because we do have an SDK and no devrel atm. As an infra project crazy stuff. :D But I also feel it whenever there's new chain integrations (we offer onchain data access/alternative to RPC for read access) there's this "hey let's do a demo for devs" - and well... all of these chains compete for the same small crowd of devs. | |
Characters remaining: 10,000 comment guidelines | |